Traffic bearer mapping method and communication device

ABSTRACT

A traffic bearer mapping method includes: obtaining attribute information of a traffic data flow of a user; selecting a relay transmission tunnel according to the attribute information of the traffic data flow of the user; and mapping the received traffic data flow to the relay transmission tunnel for transmission, where the relay transmission tunnel includes a relay link radio bearer Un RB or a bearer including the Un RB. Transmission of a traffic data flow in an LTE-A network after a relay node is introduced into is implemented, thereby ensuring quality of service of multi-service.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/330,311, filed on Dec. 19, 2011, which is a continuation ofInternational Application No. PCT/CN2010/074036, filed on Jun. 18, 2010.The International application claims priority to Chinese PatentApplication No. 200910139406.7, filed on Jun. 19, 2009. Theafore-mentioned patent applications are hereby incorporated by referencein their entireties.

FIELD OF THE INVENTION

The present invention relates to the field of communicationtechnologies, and in particular, to a traffic bearer mapping method anda communication device.

BACKGROUND OF THE INVENTION

A conventional cellular network (for example, an LTE network) is asingle-hop network using a base station as a center, that is, data isdirectly interactively transmitted between the base station (eNB,Evolved Node Base Station) and a user equipment (UE, User Equipment).After a relay node (RN, Relay node) is introduced into an LTE-Aprotocol, multi-hop transmission exists in the interactive transmissionof data between the base station and the user equipment, that is, theinteractive transmission of data between the base station and the userequipment is required to pass through the relay node RN. As shown inFIG. 1, in an LTE-A network after the relay node RN is introduced, atransmission link between the user equipment and the base station may bedivided into two segments, that is,

an access link Uu, which is an air interface link between the userequipment and the directly associated relay node RN; and

a relay link Un, which is an air interface link between the relay nodeRN and the base station eNB.

In an existing LTE network, in order to ensure quality of service (Qos,Quality of Service) of multi-service, a traffic bearer mapping mechanismis introduced. The bearer mapping of the traffic data flow in an LTEnetwork is as shown in FIG. 2, where the LTE network includes a userequipment 1, a base station 2, a serving gateway (S-GW, Serving Gateway)3, and a packet data network gateway (P-GW, PDN Gateway) 4. A Un radiobearer (Uu RB, Uu Radio Bearer) 5, an S1 bearer 6, and an S5/S8 bearer 7that correspond to the user equipment 1 form an evolved packet system(EPS, Evolved Packet System) bearer. Trapezoid frames in the userequipment 1 and the packet data network gateway 4 represent a trafficflow template (TFT, Traffic Flow Template) operation.

An uplink traffic bearer mapping process in the existing LET network isas follows: The user equipment 1 maps the uplink traffic flow to an EPSbearer through an uplink traffic flow template (UL TFT, Uplink TrafficFlow Template); a one-to-one mapping between the UL TFT and the Uu radiobearer 5 is implemented by the user equipment 1 creating a bindingbetween the uplink traffic data flow and the Uu radio bearer 5; aone-to-one mapping between the Uu radio bearer 5 and the S1 bearer 6 isimplemented by the base station 2 creating a binding between the Uuradio bearer 5 and the S1 bearer 6; and a one-to-one mapping between theS1 bearer 6 and the S5/S8 bearer 7 is implemented by the S-GW creating abinding between the S1 bearer 6 and the S5/S8 bearer 7. Finally, the EPSbearer that transmits the data is cascaded by the Un radio bearer 5, theS1 bearer 6 and the S5/S8 bearer 7 and implements that the userequipment 1 supports a PDN connecting service between external PDNnetworks, thereby ensuring the QoS of multi-service. The relationshipsamong the Uu radio bearer 5, the S1 bearer 6, and the S5/S8 bearer 7 areone-to-one mapping relationships.

As for the LTE-A network after the relay node RN is introduced, a Unradio bearer (Un RB, Un Radio Bearer) configured to support relaytransmission exists on the relay link. The bearer mapping solution ofthe traffic flow in the existing LTE network cannot implement thetransmission of the traffic data flow in the LTE-A network after therelay node RN is introduced, and therefore the QoS of the multi-servicecannot be ensured.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a traffic bearer mappingmethod and a communication device, so as to implement transmission of atraffic data flow in an LTE-A network after a relay node is introduced,thereby ensuring QoS of multi-service.

The traffic bearer mapping method and the communication device providedin the present invention are implemented as follows.

A traffic bearer mapping method includes:

obtaining attribute information of a traffic data flow of a user; and

selecting a relay transmission tunnel according to the attributeinformation of the traffic data flow of the user, and mapping thereceived traffic data flow to the relay transmission tunnel fortransmission, where the relay transmission tunnel includes a Un RB or abearer including the Un RB.

A traffic bearer mapping method includes:

de-mapping a received traffic data flow, and restoring the traffic dataflow corresponding to a user, where the received traffic data flow issent by a peer end node through a relay transmission tunnel, and therelay transmission tunnel is selected by the peer end node according toattribute information of the traffic data flow of the user, and includesa relay link radio bearer Un RB or a bearer including the Un RB; and

mapping the traffic data flow corresponding to the user to apredetermined bearer for transmission.

A communication device includes:

an obtaining unit, configured to obtain attribute information of atraffic data flow of a user;

a selecting unit, configured to select a relay transmission tunnelaccording to the attribute information of the traffic data flow of theuser; and

a first mapping unit, configured to map the received traffic data flowto the relay transmission tunnel for transmission, where the relaytransmission tunnel includes a Un RB or a bearer including the Un RB.

A communication device includes:

a de-mapping unit, configured to de-map a received traffic data flow,and restore the traffic data flow corresponding to a user, where thereceived traffic data flow is sent by a peer end node through a relaytransmission tunnel, and the relay transmission tunnel is selected bythe peer end node according to attribute information of the traffic dataflow of the user, and includes a Un RB or a bearer including the Un RB;and

a second mapping unit, configured to map the traffic data flowcorresponding to the user to a predetermined bearer for transmission.

In can be seen from the forgoing technical solutions provided in theembodiments of the present invention that, an embodiment of the presentinvention provides a traffic bearer mapping method in an LTE-A networkafter an relay node is introduced, so as to implement the transmissionof the traffic data flow in the LTE-A network, thereby ensuring the QoSof multi-service.

DETAILED DESCRIPTION OF THE DRAWINGS

To illustrate the technical solutions in the embodiments of the presentinvention clearer, the accompanying drawings for describing theembodiments or the prior art are introduced briefly in the following.Apparently, the accompanying drawings in the following description areonly some embodiments of the present invention, and persons of ordinaryskill in the art may further derive other drawings according to theaccompanying drawings without creative efforts.

FIG. 1 is a schematic diagram of an LTE-A network in the prior art;

FIG. 2 is a schematic diagram of bearer mapping of a traffic data flowin an LTE network in the prior art;

FIG. 3 is a flow chart of a traffic bearer mapping method according toan embodiment of the present invention;

FIG. 4 is a flow chart of another traffic bearer mapping methodaccording to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a protocol stack architecture 1 wherean S1 bearer terminates at an eNB according to an embodiment of thepresent invention;

FIG. 6 is a schematic diagram of a protocol stack architecture 2 wherean S1 bearer terminates at an eNB according to an embodiment of thepresent invention;

FIG. 7 is a schematic diagram of a protocol stack architecture 1 wherean S1 bearer terminates at an RN according to an embodiment of thepresent invention;

FIG. 8 is a schematic diagram of a protocol stack architecture 2 wherean S1 bearer terminates at an RN according to an embodiment of thepresent invention;

FIG. 9 is a flow chart of an uplink traffic bearer mapping method in thecase of a protocol stack architecture 1 where an S1 bearer terminates atan eNB according to an embodiment of the present invention;

FIG. 10 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 11 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 12 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 13 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 14 is a schematic diagram of a format of a multiplexed data packetat an MAC layer according to an embodiment of the present invention;

FIG. 15 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 16 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 17 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 18 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 19 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention;

FIG. 20 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention;

FIG. 21 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention;

FIG. 22 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention;

FIG. 23 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention;

FIG. 24 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an RN according to an embodiment of the present invention;

FIG. 25 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an RN according to an embodiment of the present invention;

FIG. 26 is a block diagram of a communication device according to anembodiment of the present invention; and

FIG. 27 is a block diagram of another communication device according toan embodiment of the present invention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

In order to make persons skilled in the art better understand thetechnical solutions of the present invention, the technical solutions inthe present invention are clearly and fully described below withreference to the accompanying drawings. Apparently, the embodiments tobe described below are merely a part rather than all of the embodimentsof the present invention. All other embodiments obtained by persons ofordinary skill in the art based on the embodiments of the presentinvention without creative efforts shall fall within protection scope ofthe present invention.

FIG. 3 is a flow chart of a traffic bearer mapping method according toan embodiment of the present invention, which includes the following.

S101: Obtain attribute information of a traffic data flow of a user.

S102: Select a relay transmission tunnel according to the attributeinformation of the traffic data flow of the user, and map the receivedtraffic data flow to the relay transmission tunnel for transmission,where the relay transmission tunnel includes a relay link radio bearerUn RB or a bearer including the Un RB.

In the bearer mapping method provided in the embodiment of presentinvention, a main execution body may be a relay node RN, andcorrespondingly, the traffic data flow is an uplink traffic data flow.In the bearer mapping method provided in the embodiment of the presentinvention, the main execution body may also be a base station eNB or apacket data network gateway P-GW of the relay node RN, andcorrespondingly, the traffic data flow is a downlink traffic data flow.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement transmission of the traffic data flow in the LTE-A network,thereby ensuring QoS of multi-service.

FIG. 4 is a flow chart of another traffic bearer mapping methodaccording to an embodiment of the present invention, which includes thefollowing.

S201: De-map a received traffic data flow, and restore the traffic dataflow corresponding to a user.

S202: Map the traffic data flow corresponding to the user to apredetermined bearer for transmission.

In the bearer mapping method provided in this embodiment, a mainexecution body may be a base station eNB, a serving gateway S-GW, or apacket data network gateway P-GW, and correspondingly, the traffic dataflow is an uplink traffic data flow. In the bearer mapping methodprovided in this embodiment, the main execution body may also be a relaynode RN, and correspondingly, the traffic data flow is a downlinktraffic data flow.

An embodiment of the present invention provide a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement transmission of the traffic data flow in the LTE-A network,thereby ensuring QoS of multi-service.

The traffic bearer mapping method provided in the embodiment of thepresent invention corresponds to a specific protocol stack architecture.The specific protocol stack architecture comprises two types as follows:One is a protocol stack architecture where a backhaul terminates at aneNB, and the other is a protocol stack architecture where the backhaulterminates at an RN. The backhaul refers to an intermediate link fromthe gateway to the base station. In the LTE-A network, the backhaulrefers to an intermediate link from the gateway to the base station orthe relay node. In the LTE-A network, the backhaul may specifically bean S1 bearer, where the S1 is an interface identifier between thegateway and the base station or the gateway and the relay node. That is,the specific protocol stack architecture includes a protocol stackarchitecture where an S1 bearer terminates at an eNB and a protocolstack architecture where an S1 bearer terminates at an RN. The S1 bearerin the following embodiments is the backhaul.

The protocol stack architecture where the S1 bearer terminates at theeNB includes a protocol stack architecture 1 where an S1 bearerterminates at an eNB and a protocol stack architecture 2 where an S1bearer terminates at an eNB, as shown in FIG. 5 and FIG. 6. Thedifference between FIG. 5 and FIG. 6 lies in that, a GTP-U sub-layer, aUDP sub-layer, and an IP sub-layer are added in a layer 3 (L3) of an RNend and an eNB end of a Un interface in FIG. 6.

The protocol stack architecture where the S1 bearer terminates at the RNincludes a protocol stack architecture 1 where an S1 bearer terminatesat an RN and a protocol stack architecture 2 where an S1 bearerterminates at an RN, as shown in FIG. 7 and FIG. 8. In FIG. 7, L3 of aUn interface side of the RN protocol stack includes an IP sub-layer, aUDP sub-layer, and a GTP-U sub-layer, and internal forwarding betweenthe Uu interface and the Un interface is performed above the GTP-Ulayer. The eNB is responsible for the internal forwarding between the Uninterface and the core network side bearer in the IP layer above thecore network layer 2 (L2). The structure of the protocol stack in theUE, the S-GW, and the P-GW is known by persons skilled in the art, andare not described in detail here. In FIG. 8, the L3 of the Un interfaceside of the RN protocol stack includes an IP sub-layer, a UDP sub-layer,and a GTP-U sub-layer, and internal forwarding between the Uu interfaceand the Un interface is performed above the GTP-U layer. The structureof the protocol stack in the UE, the eNB, the S-GW, and the P-GW isknown by persons skilled in the art, and are not described in detailhere.

As for the protocol stack architecture 1 where the S1 bearer terminatesat the eNB, the S1 bearer transmits the EPS bearer data of the UEbetween the eNB and the S-GW.

FIG. 9 is a flow chart of an uplink traffic bearer mapping method in thecase of a protocol stack architecture 1 where an S1 bearer terminates atan eNB according to an embodiment of the present invention, whichincludes the following.

S301: A UE maps an uplink traffic data flow to an EPS bearer fortransmission through a UL TFT (UE), creates a binding between the UL TFT(UE) and a Uu RB, maps the uplink traffic data flow to the Uu RB andtransmits the uplink traffic data flow to an RN.

The UE analyzes a Un GTP/IP header of a data packet in the uplinktraffic data flow of an IP layer of the UE through the UL TFT (UE),matches an attributes of EPS bearer according to an analysis result, andmaps the uplink traffic data flow to a successfully matched EPS bearerfor transmission. The relationship between the EPS bearer and the Uu RBis a one-to-one mapping relationship. Each EPS bearer on the Uuinterface is mapped to a Uu RB, and therefore the uplink traffic dataflow is also correspondingly mapped to a Un RB and is transmitted to theRN.

After creating the binding between the UL TFT (UE) and the Uu RB, the UErecords the mapping relationship between the UL TFT (UE) and the Uu RB,thereby creating an uplink mapping between the uplink traffic data flowand the Uu RB.

S302: The RN analyzes a data packet header of the data packet in theuplink traffic data flow through the UL TFT (RN), obtains attributeinformation of the traffic data flow of the user, and selects a Un RBaccording to the attribute information of the traffic data flow of theuser.

The relationship between the Uu RB and the Un RB is a many-to-onemapping relationship.

The data packet header includes, but is not limited to, a user datagramprotocol/Internet protocol header of a user (UE UDP/IP), where the UDP(User Datagram Protocol) is a user datagram protocol.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, or a service typeidentifier.

The selecting the Un RB according to the attribute information of thetraffic data flow of the user specifically is: matching the attributeinformation of the traffic data flow of the user with an attributeparameter of the Un RB, and selecting a successfully matched Un RB asthe predetermined Un RB, where the attribute parameter of the Un RBincludes, but is not limited to, a QoS parameter and/or a Un RBidentifier (Un RB ID).

S303: The eNB de-maps the uplink traffic data flow through the UL TFT(UE), restores the uplink traffic data flow corresponding to the user,and maps the uplink traffic data flow corresponding to the user to thecorresponding S1 bearer to transmit the uplink traffic data flow to anS-GW.

The de-mapping is a one-to-many de-mapping, and the relationship betweenthe S1 bearer and the Un RB is a many-to-one mapping relationship.

After creating the binding between the UL TFT (UE) and the S1 bearer,the eNB records the mapping relationship between the UL TFT (UE) and theS1 bearer, thereby creating an uplink mapping between the Un RB and theS1 bearer.

The creating, by the eNB, the binding between the UL TFT (UE) and the S1bearer includes the following.

The eNB analyzes the UE UDP/IP header of the data packet in the uplinktraffic data flow through the UL TFT (UE), obtains the attributeinformation of the traffic data flow of the user, selects a matched S1bearer according to the attribute information of the traffic data flowof the user, and binds the UL TFT (UE) and the matched S1 bearer.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, and a service typeidentifier.

S304: The S-GW maps the traffic data flow corresponding to the user toan S5/S8 bearer to transmit the traffic data flow to a P-GW.

The relationship between the S1 bearer and the S5/S8 bearer is aone-to-one mapping relationship.

FIG. 10 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S401: A P-GW maps a downlink traffic data flow to an EPS bearer fortransmission through a downlink traffic flow template of a user DL TFT(UE) (Downlink Traffic Flow Template (UE)), creates a binding betweenthe DL TFT (UE) and an S5/S8 bearer, and maps the downlink traffic dataflow to the S5/S8 bearer to transmit the downlink traffic data flow toan S-GW.

The P-GW analyzes a UE UDP/IP header of a data packet in the downlinktraffic data flow through the DL TFT (UE), matches the UE UDP/IP headerwith an attribute of the EPS bearer according to an analysis result, andmaps the downlink traffic data flow to a successfully matched EPS bearerfor transmission. A relationship between the EPS bearer and the S5/S8bearer is a one-to-one mapping relationship. Each EPS bearer on theS5/S8 interface is mapped to an S5/S8 bearer, and therefore the downlinktraffic data flow is also correspondingly mapped to an S5/S8 bearer andis transmitted to the S-GW.

After creating the binding between the DL TFT (UE) and the S5/S8 bearer,the P-GW records the mapping relationship between the DL TFT (UE) andthe S5/S8 bearer, thereby creating a downlink mapping between thedownlink traffic data flow and the S5/S8 bearer.

S402: The S-GW maps the downlink traffic data flow to an S1 bearer totransmit the downlink traffic data flow to an eNB.

The relationship between the S1 bearer and the S5/S8 bearer is aone-to-one mapping relationship.

S403: The eNB analyzes a data packet header of the data packet in thedownlink traffic data flow through the DL TFT (RN), obtains attributeinformation of the traffic data flow of the user, and selects a Un RBaccording to the attribute information of the traffic data flow of theuser.

The relationship between the S1 bearer and the Un RB is a many-to-onemapping relationship.

The data packet header includes, but is not limited to, a UE UDP/IPheader.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, and a service typeidentifier.

The selecting the Un RB according to the attribute information of thetraffic data flow of the UE specifically is: matching the attributeinformation of the traffic data flow of the user with an attributeparameter of the Un RB, and selecting a successfully matched Un RB asthe predetermined Un RB, where the attribute parameter of the Un RBincludes, but is not limited to, a QoS parameter and/or a Un RBidentifier (Un RB ID).

S404: An RN de-maps the downlink traffic data flow through the DL TFT(UE), restores the downlink traffic data flow corresponding to the user,and maps the downlink traffic data flow corresponding to the user to acorresponding Uu RB to transmit the downlink traffic data flow to theUE.

The de-mapping is a one-to-many de-mapping, and the relationship betweenthe Uu RB and the Un RB is a many-to-one mapping relationship.

After creating the binding between the DL TFT (UE) and the Uu RB, the RNrecords the mapping relationship between the DL TFT (UE) and the Uu RB,thereby creating a downlink mapping between the Un RB and the Uu RB.

The creating, by the RN, the binding between the DL TFT (UE) and the UuRB includes the following.

The RN analyzes the UE UDP/IP header of the data packet in the downlinktraffic data flow through the DL TFT (UE), obtains the attributeinformation of the traffic data flow of the user, selects a matched UuRB according to the attribute information of the traffic data flow ofthe user, and binds the DL TFT (UE) and the matched Uu RB.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, and a service typeidentifier.

The bearer binding operation in the uplink/downlink bearer mapping maybe implemented in an EPS bearer setup/modifying process of the UE, andan information element IE (Information Element) indication needs to beadded in the EPS bearer setup/modifying process of the UE, where theinformation element IE indication includes, but is not limited to, abearer binding relationship and identifier mapping information.

In order to enable the eNB and the RN to obtain update information ofthe UE TFT, the information element IE indication of the UE. TFT needsto be added in an existing uplink and downlink information interactionprocess, so as to notify the eNB and the RN, where the informationelement IE indication of the UE TFT includes TFT attribute informationof the UE.

An entity equipment of the core network (an MME (Mobility ManagementEntity)/an S-GW/a P-GW) may notify the eNB of the update information ofthe UE TFT in the downlink information interaction, and then the eNBnotifies the RN of the update information of the UE TFT through the Uninterface information; or the UE notifies the RN of the updateinformation of the UE TFT in the uplink information interaction, andthen the RN delivers the update information of the UE TFT to the eNB andthe entity equipment of the core network.

Similarly, in order to enable the eNB to obtain the necessary updateinformation of the RN TFT, the information element IE indication of theRN TFT needs to be added in the existing uplink and downlink informationinteraction process, so as to notify the eNB the information element IEindication of the RN TFT includes TFT attribute information of the RN.

The entity equipment of the core network may notify the eNB and the RNof the update information of the RN TFT in the downlink informationinteraction; or the RN notifies the eNB of the update information of theRN TFT, and then the eNB delivers the update information to the entityequipment of the core network.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of the traffic data flow in the LTE-Anetwork, thereby ensuring the QoS of multi-service.

FIG. 11 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S501: a UE maps an uplink traffic data flow to an EPS bearer fortransmission through a UL TFT (UE), creates a binding between the UL TFT(UE) and a Uu RB, and maps the uplink traffic data flow to the Uu RB totransmit the uplink traffic data flow to an RN.

Step 501 is to the same as step 301, and is not described in detailhere.

S502: The RN maps the uplink traffic flow to the Un RB which is boundwith the Uu RB to transmit the uplink traffic data flow to an eNB.

The relationship between the Uu RB and the Un RB is a many-to-onemapping relationship.

Before the uplink traffic data flow is transmitted, a core network endand an RN end perform control signaling interaction, where the controlsignaling includes attribute information of the traffic data flow of theuser of the uplink traffic data flow to be transmitted, and the controlsignaling interaction process includes an EPS bearer setup/modifyingprocess.

One or more Un RBs for bearer mapping exist on the Un, and the RN bindseach Uu RB with a specific Un RB according to a relevant criterion (forexample, a QoS parameter), which is specifically as follows.

The RN obtains the attribute information of the traffic data flow of theuser from the control signaling interaction process, matches theattribute information of the traffic data flow of the user withattribute information of the Un RB according to the attributeinformation of the traffic data flow of the user, and performs bearerbinding between a successfully matched Un RB and the Uu RB transmittingthe uplink traffic data flow.

The attribute information of the traffic data flow of the user includes,but is not limited to, a QoS parameter and/or a Uu RB ID, and theattribute information of the Un RB includes, but is not limited to, aQoS parameter and/or a Un RB ID.

In the embodiment of the present invention, the bearer binding betweenthe Uu RB and the Un RB directly performs association by utilizingrespective identifiers of the two bearers, and the association is aunidirectional association. For example, supposing a bearer bindingbetween A and B is performed, the data transmitted from a bearer A isdirectly delivered to a bearer B for transmission; and on the contrary,the data transmitted from the bearer B cannot be directly delivered tothe bearer A for transmission.

When the bearer binding between the Uu RB and the specific Un RB isperformed, the uplink data transmitted from the Uu RB is directlydelivered to the Un RB for transmission.

S503: The eNB de-maps the uplink traffic data flow through the UL TFT(UE), restores the uplink traffic data flow corresponding to the user,and maps the uplink traffic data flow corresponding to the user to an S1bearer to transmit the uplink traffic data flow to an S-GW.

Step 503 is the same as step 303, and is not described in detail here.

S504: The S-GW maps the traffic data flow corresponding to the user toan S5/S8 bearer to transmit the traffic data flow to a P-GW.

The relationship between the S1 bearer and the S5/S8 bearer is aone-to-one mapping relationship.

FIG. 12 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S601: A P-GW maps a downlink traffic data flow to an EPS bearer fortransmission through a downlink traffic flow template of a user DL TFT(UE), creates a binding between the DL TFT (UE) and an S5/S8 bearer, andmaps the downlink traffic data flow to the S5/S8 bearer to transmit thedownlink traffic data flow to an S-GW.

Step 601 is the same as step 401, and is not described in detail here.

S602: The S-GW maps the downlink traffic flow to an S1 bearer totransmit the downlink traffic data flow to an eNB.

The relationship between the S1 bearer and the S5/S8 bearer is aone-to-one mapping relationship.

S603: The eNB maps the downlink traffic data flow to the Un RB which isbound with the S1 bearer to transmit the downlink traffic data flow toan RN.

The relationship between the S1 bearer and the Un RB is a many-to-onemapping relationship.

Before the uplink traffic data flow is transmitted, a core network endand an eNB end perform control signaling interaction, where the controlsignaling includes attribute information of the traffic data flow of theuser of the uplink traffic data flow to be transmitted, and the controlsignaling interaction process includes an EPS bearer setup/modifyingprocess.

One or more Un RBs for bearer mapping exist on the Un, and the eNB bindseach S1 bearer with a specific Un RB according to a relevant criterion(for example, a QoS parameter), which is specifically as follows.

The eNB obtains the attribute information of the traffic data flow ofthe user from the control signaling interaction process, matches theattribute information of the traffic data flow of the user withattribute information of the Un RB according to the attributeinformation of the traffic data flow of the user, and performs bearerbinding between a successfully matched Un RB and the S1 bearertransmitting the downlink traffic data flow.

The attribute information of the traffic data flow of the user includesa QoS parameter and/or an S1 TEID, and the attribute information of theUn RB includes a QoS parameter and/or a Un RB ID.

In the embodiment of the present invention, the essence of the bearerbinding of the S1 bearer and the Un RB and the bearer binding of the UuRB and the Un RB is the same, and is not described here.

S604: The RN de-maps the downlink traffic data flow through the DL TFT(UE), restores the downlink traffic data flow corresponding to the user,and maps the downlink traffic data flow corresponding to the user to theS1 bearer to transmit the downlink traffic data flow to the UE.

Step 604 is the same as step 404, and is not described in detail here.

The bearer binding operation in the uplink/downlink bearer mapping maybe implemented in an EPS bearer setup/modifying process of the UE, andan information element IE indication needs to be added in the EPS bearersetup/modifying process of the UP, where the information element IEindication includes, but is not limited to, a bearer bindingrelationship and identifier mapping information.

In order to enable the eNB and the RN to obtain the update informationof the UE TFT, the information element IE indication of the UP TFT needsto be added in an existing uplink and downlink information interactionprocess, so as to notify the eNB and the RN, where the informationelement IE indication of the UE TFT includes attribute information ofthe UE TFT.

An entity equipment of the core network (an MME (Mobility ManagementEntity)/an S-GW/a P-GW) may notify the eNB of the update information ofthe UE TFT in the downlink information interaction, and then the eNBnotifies the RN of the update information of the UE TFT through the Uninterface information; or the UE notifies the RN of the updateinformation of the UE TFT in the uplink information interaction, andthen the RN delivers the update information of the UE TFT to the eNB andthe entity equipment of the core network.

Similarly, in order to enable the eNB to obtain the necessary updateinformation of the RN TFT, the information element IE indication of theRN TFT needs to be added in the existing uplink and downlink informationinteraction process, so as to notify the eNB, where the IE indication ofthe RN TFT includes attribute information of the RN TFT.

The entity equipment of the core network may notify the eNB and the RNof the update information of the RN TFT in the downlink informationinteraction; or the RN notifies the eNB of the update information of theRN TFT, and then the eNB delivers the update information to the entityequipment of the core network.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of the traffic data flow in the LTE-Anetwork, thereby ensuring the QoS of multi-service.

As for the protocol stack architecture 1 where an S1 bearer terminatesat an eNB, the S1 bearer transmits the EPS bearer data of the UE betweenthe eNB and the S-GW.

FIG. 13 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S701: A UE maps a uplink traffic data flow to an EPS bearer fortransmission through an UL TFT (UE), creates a binding between the ULTFT (UE) and a Uu RB, and maps the uplink traffic data flow to the Uu RBto transmit the uplink traffic data flow to an RN.

Step 701 is the same as step 301, and is not described in detail here.

S702: The RN maps the uplink traffic data flow to a Un RB to transmitthe uplink traffic data flow to an eNB.

Before the uplink traffic flow data is transmitted, the RN obtainsattribute information of the traffic data flow of the user from acontrol signaling interaction process, where the control signalinginteraction process includes an EPS bearer setup/modifying process.

The RN receives the uplink traffic data flow on the Uu interface,obtains an MAC protocol data unit PDU (Protocol Data Unit) aftermultiplexing a data packet in the uplink traffic data flow at a mediaaccess control (MAC, Media Access Control) layer, and maps the MAC PDUto a predetermined Un physical channel. The Un physical channel is atransmission entity of the Un RB at a physical layer, and the uplinktraffic data flow may include traffic data flows of different UEs.

The MAC PDU includes a predetermined identifier, and the predeterminedidentifier may uniquely determine which UE a payload part in the datapacket belongs to and an EPS bearer corresponding to the UE.

The predetermined identifier may be newly added with a UE ID on thebasis of an existing logical channel identifier, and the range of theexisting logical channel identifier may be extended, so that thepredetermined identifier may uniquely correspond to a certain EPS bearerof a certain UE, or may indicate the UE and a new identifier of the EPSbearer corresponding to the UE.

FIG. 14 is a schematic diagram of a format of a multiplexed data packetat an MAC layer according to an embodiment of the present invention. Asshown in FIG. 14, an MAC header includes a plurality of MAC sub-headers,and each MAC sub-header correspondingly describes each data block of anMAC payload region. A first MAC sub-header corresponds to an MAC controlelement 1, where the MAC control element has the same function with anMAC service data unit SDU (Service Data Unit), and also represents adata block. An LCID (Logical Channel ID) in the MAC sub-header is alogical channel identifier. L (length) is a length indication field, andrepresents the length of the data block corresponding to the MAC payloadregion. F (Format) is a format indication field and is configured toindicate a bit number (7 bits or 15 bits) which describes the length ofthe data block. E (Extension) is an extension field and is configured toindicate whether a part of an MAC header ends, R (Reserved) is areserved bit, and is set to zero in the LTE.

The selecting the predetermined Un physical channel specifically is:matching the attribute information of the traffic data flow of the userwith the predetermined mapping relationship of the Un physical channel,and selecting a successfully matched Un physical channel as thepredetermined Un physical channel.

The attribute information of the traffic data flow of the user includes,but is not limited to, a QoS parameter of the traffic flow of the userand/or a type of the logical channel transmitting the traffic data flowof the user. The predetermined mapping relationship includes, but is notlimited to, a mapping criterion between the logical channel and thephysical channel defined in the LTE or LTE-A specification.

S703: The eNB de-maps the MAC PDU, restores the uplink traffic data flowcorresponding to the user, and maps the uplink traffic data flowcorresponding to the user to an S1 bearer to transmit the uplink trafficdata flow to an S-GW.

The eNB de-multiplexes the data in the MAC PDU to restore the uplinktraffic data flow corresponding to the user according to the logicalchannel mapping relationship and the UE ID information in the MAC PDU,where the uplink traffic data flow corresponding to the user correspondsto different UE EPS bearers, and maps the UL traffic data flowcorresponding to the user to the S1 bearer for transmission according tothe one-to-one corresponding relationship between the UE EPS bearer andthe S1 bearer.

S704: The S-GW maps the traffic data flow corresponding to the user toan S5/S8 bearer to transmit the traffic data flow to a P-GW.

The relationship between the S1 bearer and the S5/S8 bearer is aone-to-one mapping relationship.

FIG. 15 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S801: A P-GW maps a downlink traffic flow to an EPS bearer fortransmission through a downlink traffic data flow of a user DL TFT (UE),creates a binding between the DL TFT (UE) and an S5/S8 bearer, and mapsthe downlink traffic data flow to the S5/S8 bearer to transmit thedownlink traffic data flow to an S-GW.

Step 801 is the same as step 401, and is not described in detail here.

S802: The S-GW maps the downlink traffic data flow to an S1 bearer totransmit the downlink traffic data flow to an eNB.

The relationship between the S1 bearer and the S5/S8 bearer is aone-to-one mapping relationship.

S803: The eNB maps the downlink traffic data flow to a Un RB to transmitthe downlink traffic data flow to an RN.

The eNB obtains an MAC PDU after multiplexing the data packet in thedownlink traffic data flow at the MAC layer according to the attributeinformation of the traffic data flow of the user, and maps the MAC PDUto a predetermined Un physical (PHY) channel. The Un physical channel isa transmission entity of the Un RB at a physical layer, and the downlinktraffic data flow may include traffic data flows of different UEs.

The MAC PDU includes a predetermined identifier, and the predeterminedidentifier may uniquely determine which UE the payload part in the datapacket belongs to and an EPS bearer corresponding to the UE.

The predetermined identifier may be newly added with a UE ID on thebasis of an existing logical channel identifier, and the range of theexisting logical channel identifier is extended, so that thepredetermined identifier may uniquely correspond to a certain EPS bearerof a certain UE, or indicates the UE and a new identifier of the EPSbearer corresponding to the UE.

The selecting the predetermined Un physical channel specifically is:matching the attribute information of the traffic data flow of the userwith the predetermined mapping relationship of the Un physical channel,and selecting a successfully matched Un physical channel as thepredetermined Un physical channel.

The attribute information of the traffic data flow of the user includes,but is not limited to, a QoS parameter of the traffic flow of the userand/or the type of the logical channel transmitting the traffic dataflow of the user. The predetermined mapping relationship includes, butis not limited to, a mapping criterion between the logical channel andthe physical channel defined in the LTE or LTE-A specification.

S804: The RN de-maps the MAC PDU, restores the downlink traffic dataflow corresponding to the user, and maps the downlink traffic data flowcorresponding to the user to a Uu bearer to transmit the downlinktraffic data flow to the user.

The RN de-multiplexes the data in the MAC PDU and restores the downlinktraffic data flow corresponding to the user according to the logicalchannel mapping relationship and the UE ID information in the MAC PDU,where the downlink traffic data flow corresponding to the usercorresponds to different UE EPS bearers, and maps the downlink trafficdata flow corresponding to the user to the Uu bearer for transmissionaccording to the one-to-one corresponding relationship between the UEEPS bearer and the Uu bearer.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of a traffic data flow in the LTE-A network,thereby ensuring the QoS of multi-service.

As for the protocol stack architecture 2 where an S1 bearer terminatesat an eNB, the S1 bearer is used to transmit the EPS bearer data of theUE between the eNB and the S-GW.

In the embodiment of the present invention, a Un GTP tunnel is set upabove the Un RB. The Un GTP tunnel connects GTP-U sub-layers of two endsof the Un interface, where the relationships among the Uu RB, the Un GTPtunnel, the S1 bearer, and the S5/S8 bearer are one-to-one mappingrelationships, and during the radio transmission through the Uninterface, the relationship between the Un GTP and the Un RB is amany-to-one mapping relationship.

FIG. 16 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S901: A UE maps an uplink traffic data flow to an EPS bearer fortransmission through a UL TFT (UE), creates a binding between the UL TFT(UE) and a Uu RB, and maps the uplink traffic data flow to the Uu RB totransmit the uplink traffic data flow to an RN.

Step 901 is the same as step 301, and is not described in detail here.

S902: The RN maps the uplink traffic data flow to the Un RB which isbound with the Un GTP tunnel to transmit the uplink traffic data flow toan eNB.

After receiving the uplink traffic data flow, the RN analyzes a dataheader of a data packet in the uplink traffic data flow at an IP layer,obtains attribute information of the traffic data flow of the user fromthe data packet. The data header includes a Un GPRS tunneling protocol(Un GTP, Un GPRS Tunneling Protocol) header, and the attributeinformation of the traffic data flow of the user includes a Un tunnelendpoint identifier (TEID, Tunnel Endpoint IDentifier).

Match the Un TEID with an attribute parameter of the Un RB according toa predetermined criterion, and bind a successfully matched Un TEID withthe attribute parameter of the Un RB, thereby implementing the bearerbinding between the Un GTP tunnel and the Un RB. The attribute parameterof the Un RB includes a QoS parameter and/or a Un RB ID.

The predetermined criterion includes, but is not limited to, a QoSrequirement.

The bearer binding operation between the Un GTP tunnel and the Un RB onthe Un may be implemented in an EPS bearer setup/modifying process ofthe UE.

S903: The eNB de-maps the uplink traffic data flow, restores the uplinktraffic data flow corresponding to the user, and maps the uplink trafficdata flow corresponding to the user to an S1 bearer to transmit theuplink traffic data flow to an S-GW.

Step 903 is the same as step 303, and is not described in detail here.

S904: The S-GW maps the traffic data flow corresponding to the user toan S5/S8 bearer to transmit the traffic data flow to a P-GW.

FIG. 17 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S1001: A P-GW maps a downlink traffic flow to an EPS bearer fortransmission through a downlink traffic flow template of a user DL TFT(UE), creates a binding between the DL TFT (UE) and an S5/S8 bearer, andmaps the downlink traffic data flow to the S5/S8 bearer to transmit thedownlink traffic data flow to an S-GW.

Step 1001 is the same as step 401, and is not described in detail here.

S1002: The S-GW maps the downlink traffic data flow to an S1 bearer totransmit the downlink traffic data flow to an eNB.

S1003: The eNB maps the downlink traffic data flow to the Un RB which isbound with the Uu GTP tunnel to transmit the downlink traffic data flowto an RN.

After receiving the downlink traffic data flow, the eNB analyzes a dataheader of a data packet in the downlink traffic data flow at an IPlayer, obtains attribute information of the traffic data flow of theuser in the data packet. The data header includes a Un GTP header, andthe attribute information of the traffic data flow of the user includesa Un TEID.

Match the Un TEID with an attribute parameter of the Un RB according toa predetermined criterion, and bind a successfully matched Un TEID withthe attribute parameter of the Un RB, thereby implementing the bearerbinding between the Un GTP tunnel and the Un RB. The attribute parameterof the Un RB includes a QoS parameter and/or a Un RB ID.

The predetermined criterion includes, but is not limited to, a QoSrequirement.

The bearer binding operation between the Un GTP tunnel and the Un RB onthe Un may be implemented in an EPS bearer setup/modifying process ofthe UE.

S1004: The RN de-maps the downlink traffic data flow, restores thedownlink traffic data flow corresponding to the user, and maps thedownlink traffic data flow corresponding to the user to a correspondingUu RB to transmit the downlink traffic data flow to the user.

Step 1004 is the same as step 404, and is not described in detail here.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of the traffic data flow in the LTE-Anetwork, thereby ensuring the QoS of multi-service.

FIG. 18 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 2 in which an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, in which the method includes the following steps.

S1101, a UE maps a UL traffic data flow to an EPS bearer fortransmission through a UL TFT (UE), creates a binding between the UL TFT(UE) and a Uu RB, and maps the UL traffic data flow to the Uu RB totransmit the UL traffic data flow to an RN.

Step 1101 is the same as step 301, and is not described in detail here.

S1102: The RN maps the uplink traffic data flow to the Un RB which isbound with the Un GTP tunnel to transmit the uplink traffic data flow toan eNB.

After receiving the uplink traffic data flow, the RN analyzes a dataheader of a data packet in the UL traffic data flow at an IP layer,obtains attribute information of the traffic data flow of the user inthe data packet. The data header includes a Un datagramprotocol/Internet protocol header of a user (Un UDP/IP), and theattribute information of the traffic data flow of the user includespredetermined information in the Un UDP/IP header.

If the RN fails to analyze the Un GTP header at the IP layer, forexample, the RN fails to analyze the Un GTP header at the IP layer whenIPsec encrypted protection is performed on the data packet of the uplinktraffic data flow, the RN is required to analyze the Un UDP/IP header atthe IP layer.

Match the predetermined information in the Un UDP/IP header with anattribute parameter of the Un RB according to a predetermined criterion,and deliver a successfully matched data packet to the corresponding UnRB for transmission, thereby implementing the bearer binding between theUn GTP tunnel and the Un RB. The attribute parameter of the Un RBincludes a QoS parameter and/or a Un RB ID.

The predetermined criterion includes, but is not limited to, a QoSrequirement.

The predetermined information in the Un UDP/IP header includes, but isnot limited to, an IP address, a port number, and service typeindicating information.

The bearer binding operation between the Un GTP tunnel and the Un RB onthe Un may be implemented in an EPS bearer setup/modifying process ofthe UE.

S1103: The eNB de-maps the uplink traffic data flow, restores the uplinktraffic data flow corresponding to the user, and maps the uplink trafficdata flow corresponding to the user to an S1 bearer to transmit theuplink traffic data flow to an S-GW.

Step 1103 is the same as step 303, and is not described in detail here.

S1104: The S-GW maps the traffic data flow corresponding to the user toan S5/S8 bearer to transmit the traffic data flow to a P-GW.

FIG. 19 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an eNB according to an embodiment of the presentinvention, which includes the following.

S1201: A P-GW maps a downlink traffic flow to an EPS bearer fortransmission through a downlink traffic flow template of a user DL TFT(UE), creates a binding between the DL TFT (UE) and an S5/S8 bearer, andmaps the downlink traffic data flow to the S5/S8 bearer to transmit thedownlink traffic data flow to an S-GW.

Step 1201 is the same as step 401, and is not described in detail here.

S1202: The S-GW maps the downlink traffic data flow to an S1 bearer totransmit the downlink traffic data flow to an eNB.

S1203: The eNB maps the downlink traffic data flow to the Un RB which isbound with the Uu GTP tunnel to transmit the downlink traffic data flowto an RN.

After receiving the downlink traffic data flow, the eNB analyzes a dataheader of a data packet in the downlink traffic data flow at an IPlayer, obtains attribute information of the traffic data flow of theuser in the data packet. The data header includes a Un UDP/IP header,and the attribute information of the traffic data flow of the userincludes predetermined information in the Un UDP/IP header.

Match the predetermined information in the Un UDP/IP header with theattribute parameter of the Un RB according to the predeterminedcriterion, and deliver a successfully matched data packet to thecorresponding Un RB for transmission, thereby implementing the bearerbinding between the Un GTP tunnel and the Un RB. The attribute parameterof the Un RB includes a QoS parameter and/or a Un RB ID.

The predetermined criterion includes, but is not limited to, a QoSrequirement.

The predetermined information in the Un UDP/IP header includes, but isnot limited to, an IP address, a port number, and service typeindicating information.

The bearer binding operation between the Un GTP tunnel and the Un RB onthe Un may be implemented in an EPS bearer setup/modifying process ofthe UE.

S1204: The RN de-maps the downlink traffic data flow, restores thedownlink traffic data flow corresponding to the user, and maps thedownlink traffic data flow corresponding to the user to a correspondingUu RB to transmit the downlink traffic data flow to the UE.

Step 1204 is the same as step 404, and is not described in detail here.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of the traffic data flow in the LTE-Anetwork, thereby ensuring the QoS of multi-service.

As for the protocol stack architecture 1 where an S1 bearer terminatesat an RN, the S1 bearer transmits the EPS bearer data of the UE betweenthe RN and the S-GW.

FIG. 20 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention,which includes the following.

S1301: A UE maps an uplink traffic data flow to an EPS bearer fortransmission through a UL TFT (UE), creates a binding between the UL TFT(UE) and a Uu RB, and maps the uplink traffic data flow to the Uu RB totransmit the uplink traffic data flow to an RN.

Step 1301 is the same as step 301, and is not described in detail here.

S1302: The RN analyzes a transport layer IP packet header of the datapacket in the uplink traffic data flow through the UL TFT (RN), obtainsattribute information of the traffic data flow of the user, and selectsthe Un RB according to the attribute information of the traffic dataflow of the UE for transmission to an eNB.

The relationship between the Uu RB and the Un RB is a many-to-onemapping relationship.

The transport layer IP packet header includes a transport layer UDP/IPheader, a GTP header, and a UE UDP/IP header. The RN may directlyanalyze the transport layer UDP/IP header of the data packet in theuplink traffic data flow through the UL TFT (RN), or may jointly analyzethe transport layer UDP/IP header, the GTP header, and the UE UDP/IPheader.

The selecting the Un RB according to the attribute information of thetraffic data flow of the user specifically is: matching the attributeinformation of the traffic data flow of the user with an attributeparameter of the Un RB, and selecting a successfully matched Un RB asthe Un RB, where the attribute parameter of the Un RB includes, but islimited to, a QoS parameter and/or a Un RB ID.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, and a service typeidentifier.

S1303: An eNB forwards the uplink traffic data flow to an S-GW.

The eNB merely performs the forwarding in the transport IP layer.

S1304: The S-GW de-maps the uplink traffic data flow, restores theuplink traffic data flow corresponding to the user, and maps the uplinktraffic data flow corresponding to the user to an S5/S8 bearer totransmit the uplink traffic data flow to a P-GW.

FIG. 21 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention,which includes the following.

S1401: A P-GW maps a downlink traffic flow to an EPS bearer fortransmission through a downlink traffic flow template of a user DL TFT(UE), creates a binding between the DL TFT (UE) and an S5/S8 bearer, andmaps the downlink traffic data flow to the S5/S8 bearer to transmit thedownlink traffic data flow to an S-GW.

Step 1401 is the same as step 401, and is not described in detail here.

S1402: The S-GW delivers the downlink traffic data flow to an eNB.

S1403: The eNB analyzes a transport layer IP packet header of the datapacket in the downlink traffic data flow through the DL TFT (RN),obtains attribute information of the traffic data flow of the user, andselects the Un RB according to the attribute information of the trafficdata flow of the UE for transmission to an RN.

The eNB analyzes a transport layer IP packet header of a data packet inthe downlink traffic data flow through the DL TFT (RN), obtains theattribute information of the traffic data flow of the user, and selectsa predetermined Un RB according to the attribute information of thetraffic data flow of the user.

The transport layer IP packet header includes a transport layer UDP/IPheader, a GTP header, and a UE UDP/IP header. The eNB may directlyanalyze the transport layer UDP/IP header of the data packet in thedownlink traffic data flow through the UL TFT (RN), or may jointlyanalyze the transport layer UDP/IP header, the GTP header, and the UEUDP/IP header.

The selecting the Un RB according to the attribute information of thetraffic data flow of the user specifically is: matching the attributeinformation of the traffic data flow of the user with an attributeparameter of the Un RB, and selecting a successfully matched Un RB asthe Un RB, where the attribute parameter of the Un RB includes, but isnot limited to, a QoS parameter and/or a Un RB ID.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, and a service typeidentifier.

S1404: The RN de-maps the downlink traffic data flow, restores thedownlink traffic data flow corresponding to the user, and maps thedownlink traffic data flow corresponding to the user to a Uu RB totransmit the downlink traffic data flow to the UE.

The restored downlink traffic data flow corresponding to the user is thetraffic data flow of the S1 bearer. The downlink traffic data flowcorresponding to the user is delivered to the UE according to theone-to-one mapping relationship between the S1 bearer and the Uu RB.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of the traffic data flow in the LTE-Anetwork, thereby ensuring the QoS of multi-service.

FIG. 22 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention,which includes the following.

S1501: A UE maps an uplink traffic data flow to an EPS bearer fortransmission through a UL TFT (UE), creates binding between a UL TFT(UE) and a Uu RB, and maps the uplink traffic data flow to a Uu RB totransmit the uplink traffic data flow to an RN.

Step 1501 is the same as step 301, and is not described in detail here.

S1502: The RN maps the uplink traffic data flow to the Un RB which isbound with the S1 bearer to transmit the uplink traffic data flow to aneNB.

Before the uplink traffic data flow is transmitted, a core network endand an RN end perform control signaling interaction, where the controlsignaling includes attribute information of the traffic data flow of theuser of the uplink traffic data flow to be transmitted, and the controlsignaling interaction process includes an EPS bearer setup/modifyingprocess.

The RN encapsulates the uplink traffic data flow received from a Uuinterface to a corresponding S1 bearer according to the one-to-onemapping relationship between the Uu RB and the S1 bearer.

The RN binds each S1 bearer with a specific Un RB according to arelevant criterion (for example, a QoS parameter), which is specificallyas follows.

The RN obtains the attribute information of the traffic data flow of theuser from the control signaling interaction process, where the attributeinformation of the traffic data flow of the user includes a TEID of theS1 bearer.

Match the TEID of the S1 bearer with the Un RB ID of the Un RB, and binda successfully matched Un RB with the corresponding S1 bearer.

The relationship between the S1 bearer and the Un RB is a many-to-onemapping relationship.

The uplink traffic data flow is delivered from the S1 bearer to the UnRB which is bound with the S1 bearer for transmission.

S1503: The eNB forwards the uplink traffic data flow to an S-GW.

The eNB merely performs the forwarding in the transport IP layer.

S1504: The S-GW de-maps the uplink traffic data flow, restores theuplink traffic data flow corresponding to the user, and maps the uplinktraffic data flow corresponding to the user to an S5/S8 bearer totransmit the uplink traffic data flow to a P-GW.

FIG. 23 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 1 where an S1 bearerterminates at an RN according to an embodiment of the present invention,which includes the following.

S1601, a P-GW maps a downlink traffic flow to an EPS bearer fortransmission through a downlink traffic flow template of a user DL TFT(UE) of the user, creates a binding between the DL TFT (UE) and an S5/S8bearer, and maps the downlink traffic data flow to the S5/S8 bearer totransmit the downlink traffic data flow to an S-GW.

Step 1601 is the same as step 401, and is not described in detail here.

S1602: The S-GW delivers the downlink traffic data flow to an eNB.

S1603: The eNB analyzes a transport layer IP packet header of the datapacket in the downlink traffic data flow through the DL TFT (RN),obtains attribute information of the traffic data flow of the user, andselects a predetermined Un RB according to the attribute information ofthe traffic data flow of the user for transmission to an RN.

The eNB analyzes a transport layer IP packet header of a data packet inthe downlink traffic data flow through the DL TFT (RN), obtains theattribute information of the traffic data flow of the user, and selectsa predetermined Un RB according to the attribute information of thetraffic data flow of the user.

The transport layer IP packet header includes a transport layer UDP/IPheader, a GTP header and a UE UDP/IP header. The eNB may directlyanalyze the transport layer UDP/IP header of the data packet in thedownlink traffic data flow through the UL TFT (RN), or may jointlyanalyze the transport layer UDP/IP header, the GTP header, and the UEUDP/IP header.

The selecting a predetermined Un RB according to the attributeinformation of the traffic data flow of the user specifically is:matching the attribute information of the traffic data flow of the userwith an attribute parameter of the Un RB, and selecting a successfullymatched Un RB as the predetermined Un RB, where the attribute parameterof the Un RB includes, but is not limited to, a QoS parameter and/or aUn RB ID.

The attribute information of the traffic data flow of the use equipmentincludes, but is not limited to, an IP address, a port number, and aservice type identifier.

S1604: An RN de-maps the downlink traffic data flow, restores thedownlink traffic data flow corresponding to the user, and maps thedownlink traffic data flow corresponding to the user to a Uu RB totransmit the DL traffic data flow to the UE.

The restored downlink traffic data flow corresponding to the user is thetraffic data flow of the S1 bearer. The downlink traffic data flowcorresponding to the user is delivered to the UE according to theone-to-one mapping relationship between the S1 bearer and the Uu RB.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of a traffic data flow in the LTE-A network,thereby ensuring the QoS of multi-service.

FIG. 24 is a flow chart of an uplink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an RN according to an embodiment of the present invention,which includes the following.

As for the protocol stack architecture 2 where an S1 bearer terminatesat an RN, the S1 bearer transmits an EPS bearer data of the UE betweenthe S-GW/P-GW of the RN and the UE.

In Embodiment 8, the EPS bearer of the RN is the bearer between the RNand the P-GW of the RN. The protocol of the P-GW of the RN is the sameas the protocol of the S-GW of the RN, and the protocol of the P-GW ofthe UE is the same as the protocol of the S-GW of the UE. In order tofacilitate description, the P-GW and the S-GW of the RN may be used asan equipment, and the P-GW and the S-GW of the UE may also be used as anequipment, as shown in FIG. 8.

In this embodiment, the P-GW and the S-GW of the UE are the same as theP-GW and the S-GW in other embodiments, and are expressed in this mannerto distinguish from P-GW of the RN and the S-GW of the RN in the presentinvention.

An uplink bear mapping process in an LTE-A network is as shown in FIG.24, which includes the following.

S1701: A UE maps an uplink traffic data flow to an EPS bearer fortransmission through a UL TFT (UE), creates a binding between a UL TFT(UE) and a Uu RB, and maps the uplink traffic data flow to a Uu RB totransmit the uplink traffic data flow to an RN.

The LIE analyzes a UE UDP/IP header of a data packet in the uplinktraffic data flow of an IP layer of the UE through the UL TFT (UE),matches the UE UDP/IP header with an attribute of the EPS beareraccording to an analysis result, and maps the uplink traffic data flowto a successfully matched EPS bearer for transmission. The EPS bearer isthe EPS bearer of the user. The relationship between the EPS bearer andthe Uu RB is a one-to-one mapping relationship. Each EPS bearer on theUu interface is mapped to a Uu RB, and therefore the uplink traffic dataflow is also correspondingly mapped to a Un RB and is transmitted to anRN.

After creating the binding between the UL TFT (UE) and the Uu RB, the UErecords a mapping relationship between the UL TFT (UE) and the Uu RB,thereby creating the uplink mapping between the uplink traffic data flowand the Uu RB.

S1702: The RN maps the uplink traffic data flow to an EPS bearer of theRN to transmit the uplink traffic data flow to the P-GW of the RN.

The mapping the uplink traffic data flow to the EPS bearer of the RNincludes the following.

The RN analyzes a transport layer IP packet header of a data packet inthe uplink traffic data flow through the UL TFT (RN), obtains attributeinformation of the traffic data flow of the user, and selects apredetermined EPS bearer of the RN according to the attributeinformation of the traffic data flow of the user.

The relationship between the Uu RB and the EPS bearer of the RN is amany-to-one mapping relationship.

The transport layer IP packet header includes a transport layer UDP/IPheader, a GTP header, and a UE UDP/IP header. The RN may directlyanalyze the transport layer UDP/IP header of the data packet in theuplink traffic data flow through the UL TFT (RN), or may jointly analyzethe transport layer UDP/IP header, the GTP header, and the UE UDP/IPheader.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, and a service typeidentifier.

The selecting the predetermined EPS bearer of the RN according to theattribute information of the traffic data flow of the user specificallyis: matching the attribute information of the traffic data flow of theuser with an attribute parameter of EPS bearer of the RN, and selectinga successfully matched EPS bearer of the RN as the predetermined EPSbearer of the RN.

The uplink traffic data flow is mapped by the RN to the predeterminedEPS bearer of the RN, and is transmitted to the P-GW of the RN throughan eNB.

S1703: The P-GW of the RN transmits the uplink traffic data flow to theP-GW of the UE, and the P-GW of the UE de-maps the uplink traffic dataflow, and restores the uplink traffic data flow corresponding to theuser.

FIG. 25 is a flow chart of a downlink traffic bearer mapping method inthe case of a protocol stack architecture 2 where an S1 bearerterminates at an RN according to an embodiment of the present invention,which includes the following

S1801: A P-GW of the UE maps a downlink traffic data flow to an EPSbearer to transmit the downlink traffic data flow to the P-GW of the RNthrough a DL TFT (UE).

The P-GW of the UE analyzes a UE UDP/IP header of a data packet in thedownlink traffic data flow of an IP layer of the UE through the DL TFT(UE), matches the UE UDP/IP header with an attribute of the EPS beareraccording to an analysis result, and maps the downlink traffic data flowto a successfully matched EPS bearer for transmission. The EPS bearer isthe EPS bearer of a UE. The relationship between the DL TFT (UE) and theEPS bearer is a one-to-one mapping relationship. The P-GW of the UEdelivers the uplink traffic data flow to the P-GW of the RN through atransport layer.

S1802: The P-GW of the RN maps the downlink traffic data flow receivedfrom the BPS bearer of the UE to the EPS bearer of the RN to transmitthe downlink traffic data flow to the RN.

The mapping the downlink traffic data flow to the predetermined EPSbearer of the RN includes the following.

The P-GW of the RN analyzes a transport layer IP packet header of a datapacket in the downlink traffic data flow through the DL TFT (RN),obtains attribute information of the traffic data flow of the user, andselects the predetermined EPS bearer of the RN according to theattribute information of the traffic data flow of the user.

The relationship between the EPS bearer of the UE and the EPS bearer ofthe RN is a many-to-one mapping relationship.

The transport layer IP packet header includes a transport layer UDP/IPheader, a GTP header, and a UE UDP/IP header. The P-GW of the RN maydirectly analyze the transport layer UDP/IP header of the data packet inthe downlink traffic data flow through the DL TFT (RN), or may jointlyanalyze the transport layer UDP/IP header, the GTP header, and the UEUDP/IP header.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, and a service typeidentifier.

The selecting the predetermined EPS bearer of the RN according to theattribute information of the traffic data flow of the user specificallyis: matching the attribute information of the traffic data flow of theuser with an attribute parameter of EPS bearer of the RN, and selectinga successfully matched EPS bearer of the RN as the predetermined EPSbearer of the RN.

The downlink traffic data flow is mapped by the P-GW of the RN to thepredetermined EPS bearer of the RN, and is transmitted to the RN throughan eNB.

S1803: An RN de-maps the downlink traffic data flow, restores thedownlink traffic data flow corresponding to the user, and maps thedownlink traffic data flow corresponding to the user to a Uu RB totransmit the downlink traffic data flow to the UE.

The de-mapping is one-to-many de-mapping.

An embodiment of the present invention provides a traffic bearer mappingmethod in an LTE-A network after a relay node is introduced, so as toimplement the transmission of the traffic data flow in the LTE-Anetwork, thereby ensuring the QoS of multi-service.

On the basis of the traffic bearer mapping method, an embodiment of thepresent invention further provides a communication device. FIG. 26 is ablock diagram of a communication device according to an embodiment ofthe present invention, which includes the following.

The obtaining unit 101 is configured to obtain attribute information ofa traffic data flow of a user.

The attribute information of the traffic data flow of the user includes,but is not limited to, an IP address, a port number, a service typeidentifier, a TEID, a UE ID, a Uu RB ID, or a logical channelidentifier.

The obtaining unit 101 includes:

a receiving sub-unit, configured to receive the traffic data flow; and

an analyzing and obtaining unit, configured to analyze a data packetheader of a data packet of the traffic data flow, and obtain theattribute information of the traffic data flow of the user from the datapacket header.

The data packet header includes, but is not limited to, a UE UDP/IPheader, a Un GTP header, or a Un UDP/IP header. In the embodiment of thepresent invention, a transport layer UDP/IP header, a GTP header, and aUE UDP/IP header in the transport layer IP packet header may also bejointly analyzed to obtain the attribute information of the traffic dataflow of the user.

As for the specific analysis of the data packet header of the datapacket of the traffic data flow, details are made to the description ofthe traffic bearer mapping method and are not described here.

Alternatively, the obtaining unit 101 may also include:

an obtaining sub-unit, configured to obtain the attribute information ofthe traffic data flow of the user from a control signaling interactionprocess, where the control signaling interaction process includes an EPSbearer setup/modifying process.

Before the traffic data flow is transmitted, a network side and the RNend or the eNB end perform control signaling interaction, where thecontrol signaling includes the attribute information of the traffic dataflow of the user of the traffic data flow to be transmitted.

The selecting unit 102 is configured to select a relay transmissiontunnel according to the attribute information of the traffic data flowof the user.

The selecting the relay transmission tunnel according to the attributeinformation of the traffic data flow of the user includes:

matching the attribute information of the traffic flow of the user withan attribute parameter of a Un RB; and selecting a successfully matchedUn RB as the relay transmission tunnel, where the attribute informationof the traffic flow of the user includes an IP address, a port number,or a service type identifier, and the attribute parameter of the Un RBinclude a QoS parameter and/or a Un RB ID.

Alternatively, the selecting the relay transmission tunnel according tothe traffic data flow of the user include:

matching the attribute information of the traffic flow of the user withthe attribute parameter of the Un RB, where the attribute information ofthe traffic flow of the user includes a Un tunnel endpoint identifierTEID, and the attribute parameter of the Un RB include the QoS parameterand/or the Un RB ID;

binding a successfully matched Un TEID with the Un RB ID to implementthe bearer binding between the Un GTP tunnel and the Un RB; and

selecting the successfully matched Un RB as the relay transmissiontunnel.

Alternatively, the selecting the relay transmission tunnel according tothe traffic data flow of the UE includes:

matching the attribute information of the traffic data flow of the userwith the attribute parameter of the EPS bearer of the RN; and

selecting a successfully matched EPS bearer of the RN as the relaytransmission tunnel, where the relay transmission tunnel includes a UnRB.

The method for selecting the relay transmission tunnel according to theattribute information of the traffic data flow of the user is the sameas the method for selecting the predetermined relay transmission tunnelin the above traffic bearer mapping method. As for the details,reference is made to the description of the above traffic bearer mappingmethod, and is not described here.

The first mapping unit 103 is configured to map the received trafficdata flow to the relay transmission tunnel for transmission, where therelay transmission tunnel includes a Un RB or a bearer including the UnRB.

The bearer including the Un RB includes an EPS bearer of an RN.

The communication device is a relay node RN, a base station eNB, or apacket data network gateway P-GW of the RN.

As for the specific method for mapping the received traffic data flow tothe relay transmission tunnel, details are made to the description ofthe above traffic bearer mapping method and are not described here.

FIG. 27 is a block diagram of another communication device according toan embodiment of the present invention, which includes:

a de-mapping unit 104, configured to de-map a received traffic data flowand restore the traffic data flow corresponding to a user; and

a second mapping unit 105, configured to map the traffic data flowcorresponding to the user to a predetermined bearer for transmission.

The communication device is a base station, a serving gateway S-GW or apacket data network gateway P-GW, or a relay node RN.

An embodiment of the present invention provides a traffic bearer mappingdevice in an LTE-A network after a relay node is introduced, so as toimplement the transmission of the traffic data flow in the LTE-Anetwork, thereby ensuring the QoS of multi-service.

Through the above descriptions of the implementation, persons skilled inthe art may clearly understand that the present invention may beaccomplished through software plus a necessary universal hardwareplatform. Based on this, the above technical solution or the part thatmakes contributions to the prior art may be substantially embodied inthe form of a software product. The computer software product may bestored in a computer readable storage medium such as a ROM/RAM, amagnetic disk or an optical disk, and include several instructions usedto instruct computer equipment (for example, a personal computer, aserver, or network equipment) to perform the method described in theembodiments of the present invention or in some parts of theembodiments.

The above descriptions are merely exemplary embodiments of the presentinvention, but are not intended to limit the present invention in anyforms. The present invention has been disclosed through exemplaryembodiments, but is not intended to be limited thereto. Any personskilled in the art may make various variations and modifications to thetechnical solutions of the present invention, or modify to equivalentembodiments with the same change by using the above disclosed methodsand technical content without departing from the scope of the technicalsolutions of the present invention. Therefore, any modification,equivalent replacement, or improvement made to the above embodiments onthe basis of the technical essence of the present invention withoutdeparting from the content of the technical solutions of the presentinvention should fall within the protection scope of the technicalsolutions of the present invention.

What is claimed is:
 1. A traffic bearer mapping method, used for a relaynode (RN) to relay a traffic data flow between a user equipment and abase station, wherein an air interface link between the RN and the basestation is a relay link (Un), and the method comprises: receiving, bythe RN, a traffic data flow from the user equipment, wherein the trafficdata flow comprises attribute information of the traffic data flow;obtaining, by the RN, the attribute information from the traffic dataflow; and selecting, by the RN, a relay transmission tunnel according tothe attribute information, wherein the relay transmission tunnelcomprises a Un radio bearer (Un RB) of which an attribute parameter ismatched with the attribute information of the traffic data flow; andmapping, by the RN, the traffic data flow to the relay transmissiontunnel for transmission.
 2. The method according to claim 1, wherein theattribute information of the traffic data flow comprises one or more ofan IP address, a port number, and a service type identifier, and theattribute parameter of the Un RB comprises at least one of a quality ofservice (QoS) parameter and a Un RB identifier (Un RB ID).
 3. The methodaccording to claim 1, wherein the attribute information of the trafficdata flow comprises one or both of a QoS parameter and an access linkradio bearer identifier (Uu RB ID), and the attribute parameter of theUn RB comprises at least one of a QoS parameter and an Un RB ID.
 4. Themethod according to claim 1, wherein the attribute information of thetraffic data flow comprises at least one of a QoS parameter and a TEIDof a backhaul, and the attribute parameter of the Un RB comprises one orboth of a QoS parameter and a Un RB ID.
 5. The method according to claim1, wherein the attribute information of the traffic data flow comprisesone of a Un tunnel endpoint identifier (TEID) or predeterminedinformation in a user datagram protocol of a Un UDP/IP header, and theattribute parameter of the Un RB comprises at least one of a QoSparameter and a Un RB ID.
 6. The method according to claim 1, whereinthe attribute information of the traffic data flow is located in a datapacket header of the traffic data flow.
 7. The method according to claim1, wherein the attribute information of the traffic data flow is locatedin a user datagram protocol/Internet protocol (UDP/IP) header.
 8. Themethod according to claim 1, wherein the attribute information of thetraffic data flow is located in a transport layer UDP/IP header.
 9. Themethod according to claim 1, wherein the RN terminates a backhaul.
 10. Atraffic bearer mapping method, used for a relay node (RN) to relay atraffic data flow between a user equipment and a base station, whereinan air interface link between the RN and the base station is a relaylink (Un), and the method comprises: generating, by the user equipment,a traffic data flow that comprises attribute information of the trafficdata flow; sending, by the user equipment, the traffic data flow to theRN, so that the RN selects a relay transmission tunnel according to theattribute information of the traffic data flow and maps the traffic dataflow to the relay transmission tunnel for transmission, wherein therelay transmission tunnel comprises a Un radio bearer (Un RB) of whichan attribute parameter is matched with the attribute information of thetraffic data flow.
 11. A communication device, located in a relay node(RN), which is used to relay a traffic data flow between a userequipment and a base station, wherein an air interface link between theRN and the base station is a relay link (Un), and the device comprises aprocessing hardware platform executing instructions stored on anon-transitory computer-readable storage medium, the instructions whenexecuted cause the device to: receive a traffic data flow from the userequipment, wherein the traffic data flow comprises attribute informationof the traffic data flow; obtain the attribute information from thetraffic data flow; and select a relay transmission tunnel according tothe attribute information, wherein the relay transmission tunnelcomprises a Un radio bearer (Un RB) of which an attribute parameter ismatched with the attribute information of the traffic data flow; and mapthe traffic data flow to the relay transmission tunnel for transmission.12. The communication device according to claim 11, wherein: theattribute information of the traffic data flow comprises one or more ofan IP address, a port number, and a service type identifier, and theattribute parameter of the Un RB comprises at least one of a quality ofservice (QoS) parameter and one of a Un RB identifier (Un RB ID); theattribute information of the traffic data flow comprises one or both ofa QoS parameter and an access link radio bearer identifier (Uu RB ID),and the attribute parameter of the Un RB comprises at least one of a QoSparameter and an Un RB ID; the attribute information of the traffic dataflow comprises one or both of a QoS parameter and a TEID of a backhaul,and the attribute parameter of the Un RB comprises at least one of a QoSparameter and a Un RB ID; or the attribute information of the trafficdata flow comprises a Un tunnel endpoint identifier (TEID) orpredetermined information in a user datagram protocol of a Un UDP/IPheader, and the attribute parameter of the Un RB comprises one or bothof a QoS parameter and a Un RB ID.
 13. The communication deviceaccording to claim 11, wherein the attribute information of the trafficdata flow is located in a data packet header of the traffic data flow.14. The communication device according to claim 11, wherein theattribute information of the traffic data flow is located in a userdatagram protocol/Internet protocol (UDP/IP) header.
 15. Thecommunication device according to claim 11, wherein the attributeinformation of the traffic data flow is located in a transport layerUDP/IP header.
 16. The communication device according to claim 11,wherein the RN terminates a backhaul.
 17. A user equipment,communicating with a base station via a relay node (RN), wherein an airinterface link between the RN and the base station is a relay link (Un),and the user equipment comprises a processing hardware platformexecuting instructions stored on a non-transitory computer-readablestorage medium, the instructions are executed which cause the userequipment to: generate a traffic data flow that comprises attributeinformation of the traffic data flow; send the traffic data flow to theRN, so that the RN selects a relay transmission tunnel according to theattribute information of the traffic data flow and maps the traffic dataflow to the relay transmission tunnel for transmission, wherein therelay transmission tunnel comprises a Un radio bearer (Un RB) of whichan attribute parameter is matched with the attribute information of thetraffic data flow.
 18. The user equipment according to claim 17,wherein: the attribute information of the traffic data flow comprisesone or more of an IP address, a port number, and a service typeidentifier, and the attribute parameter of the Un RB comprises at leastone of a quality of service (QoS) parameter and a Un RB identifier (UnRB ID); the attribute information of the traffic data flow comprises oneor both of a QoS parameter and an access link radio bearer identifier(Uu RB ID), and the attribute parameter of the Un RB comprises one orboth of a QoS parameter and an Un RB ID; the attribute information ofthe traffic data flow comprises one or both of a QoS parameter and aTEID of a backhaul, and the attribute parameter of the Un RB comprisesone or both of a QoS parameter and a Un RB ID; or the attributeinformation of the traffic data flow comprises a Un tunnel endpointidentifier (TEID) or predetermined information in a user datagramprotocol of a Un UDP/IP header, and the attribute parameter of the Un RBcomprises one or both of a QoS parameter and a Un RB ID.
 19. Thecommunication device according to claim 17, wherein the attributeinformation of the traffic data flow is located in a data packet headerof the traffic data flow.
 20. The communication device according toclaim 17, wherein the attribute information of the traffic data flow islocated in a user datagram protocol/Internet protocol (UDP/IP) header.